Resolves #20

Thanks for the implementation! A few things I'd like adjusted before merging:

• The hover effect currently seems to be attached to the entire score container rather than just the score text itself. Since the hover area is noticeably larger than the visible text, could you make the trigger area match the score text more closely?

• On mobile screens, the score breakdown tooltip overflows outside the viewport (towards the right side). Please ensure it remains fully visible on smaller devices.
• The tooltip text could be changed from white to a slightly muted/faint green to better match the rest of the UI.
• The border radius feels a bit large. Could you knock it back a few pixels?
• One more UX suggestion: currently the tooltip remains visible when moving the cursor from the score text onto the tooltip itself. Since the tooltip is purely informational and doesn't contain any interactive elements, I think it would be better if it disappeared as soon as the cursor leaves the score text.

yeah sure! I will work on it

Resolves #20
Addressed all requested changes. Let me know if anything else is needed.

One subtle idea could be to add a small downward caret next to each score value, for example:

245 ▾
180 ▾
162 ▾

Many websites use a caret/chevron to indicate that additional information is available on hover or interaction. Since the score column already has an info icon explaining the scoring formula, the caret would specifically suggest that each individual score has its own details available, without adding much visual clutter to the leaderboard.

That sounds like a reasonable and clean approach!

Feel free to go ahead with the caret indicator. Also, please make sure the interaction works well on mobile devices.

Once that's in place, I think we'll be in a good position to merge.

Thanks for working through all the feedback on this one!

I took the liberty of making one small tweak before merging and changed the caret indicator to a > symbol, as I felt it fit the terminal-style theme of the project a bit better. Other than that, the implementation looks great.